Media capture lock affordance for graphical user interface

ABSTRACT

The disclosed embodiments are directed to a media capture lock affordance for a graphical user interface displayed by a media capture device. The media capture lock affordance allows a user to lock and unlock a capture state of the media capture device using a simple and intuitive touch gesture that can be applied by the user&#39;s finger (e.g., the user&#39;s thumb) while holding the media capture device in one hand.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/271,583, entitled “Media Capture Lock Affordance for Graphical UserInterface”, filed on Feb. 8, 2019, which claims priority to U.S.Provisional Application No. 62/802,603, entitled “Media Capture LockAffordance for Graphical User Interface”, filed on Feb. 7, 2019 and is acontinuation-in-part of U.S. patent application Ser. No. 15/995,040,entitled “Media Capture Lock Affordance for Graphical User Interface”,filed on May 31, 2018, which claims priority to U.S. ProvisionalApplication No. 62/628,825, entitled “Media Capture Lock Affordance forGraphical User Interface”, filed on Feb. 9, 2018. The content of theseapplications is hereby incorporated by reference in their entirety.

FIELD

This disclosure relates generally to graphical user interfaces for mediacapture applications.

BACKGROUND

Media capture devices (e.g., smart phones, tablet computers), includeapplications that allow users to record media clips (e.g., video clips,audio clips) using one or more embedded cameras and microphones. Theuser holds down a virtual record button to capture a media clip. Oncethe user is done recording, the user can drag the media clip into adesired order with other media clips and add filters, emoji, animatedicons and titles. Media clips can be shared indirectly through socialnetworks and/or sent directly to friends through, for example, instantmessaging applications.

BRIEF SUMMARY

Some techniques for performing media capture using electronic devices,however, are generally cumbersome and inefficient. For example, someexisting techniques use a complex and time-consuming user interface,which may include multiple key presses or keystrokes. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for performinggesture-dependent media capture. Such methods and interfaces optionallycomplement or replace other methods for performing gesture-dependentmedia capture. Such methods and interfaces reduce the cognitive burdenon a user and produce a more efficient human-machine interface. Forbattery-operated computing devices, such methods and interfaces conservepower and increase the time between battery charges. Additionally, suchmethods and interfaces reduce the number of unnecessary or extraneoususer inputs in order to perform media capture, saving the user time andsaving the device energy.

The disclosed embodiments are directed to a media capture lockaffordance for a graphical user interface. In an embodiment, a method ofcapturing media comprises: detecting, by a media capture device, a tapand hold gesture input directed to a media capture affordance displayedat a first location on a graphical user interface presented on a displayscreen of the media capture device; responsive to the tap and holdgesture input, initiating, by the media capture device, a media capturesession on the media capture device in an unlocked state; responsive tothe media capture device detecting a first lift gesture in which the tapand hold gesture input lifts from the first location on the graphicaluser interface during the media capture session, terminating, by themedia capture device, the media capture session; responsive to the mediacapture device detecting a slide gesture input in which the mediacapture affordance slides from the first location to a second locationon the graphical user interface during the media capture session,changing, by the media capture device, the media capture affordance to amedia capture lock affordance; and responsive to the media capturedevice detecting a second lift gesture in which the slide gesture inputlifts from the graphical user interface at the second location duringthe media capture session, transitioning, by the media capture device,the media capture session into a locked state.

Other embodiments can include an apparatus, computing device andnon-transitory, computer-readable storage medium.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium has instructions stored thereon that when executed by amedia capture device, causes the media capture device to performoperations comprising: detecting, by the media capture device, a tap andhold gesture input directed to a media capture affordance displayed at afirst location on a graphical user interface presented on a displayscreen of the media capture device; responsive to the tap and holdgesture input, initiating, by the media image capture device, a mediacapture session on the media capture device in an unlocked media sessioncapture state; responsive to the media capture device detecting a firstlift gesture in which the tap and hold gesture input lifts from thefirst location on the graphical user interface during the media capturesession, terminating, by the media image capture device, the mediacapture session; responsive to the media capture device detecting aslide gesture input in which the media capture affordance slides fromthe first location to a second location on the graphical user interfaceduring the media capture session, changing, by the media capture device,the media capture affordance to a media capture lock affordance; andresponsive to the media capture device detecting a second lift gesturein which the slide gesture input lifts from the graphical user interfaceat the second location during the media capture session, transitioning,by the media capture device, the media capture session into a lockedmedia capture session state.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium has instructions stored thereon that when executed by a mediacapture device, causes the media capture device to perform operationscomprising: detecting, by the media capture device, a tap and holdgesture input directed to a media capture affordance displayed at afirst location on a graphical user interface presented on a displayscreen of the media capture device; responsive to the tap and holdgesture input, initiating, by the media image capture device, a mediacapture session on the media capture device in an unlocked media sessioncapture state; responsive to the media capture device detecting a firstlift gesture in which the tap and hold gesture input lifts from thefirst location on the graphical user interface during the media capturesession, terminating, by the media image capture device, the mediacapture session; responsive to the media capture device detecting aslide gesture input in which the media capture affordance slides fromthe first location to a second location on the graphical user interfaceduring the media capture session, changing, by the media capture device,the media capture affordance to a media capture lock affordance; andresponsive to the media capture device detecting a second lift gesturein which the slide gesture input lifts from the graphical user interfaceat the second location during the media capture session, transitioning,by the media capture device, the media capture session into a lockedmedia capture session state.

In accordance with some embodiments, a media capture device isdescribed. The media capture device comprises: a touch screen; one ormore processors; memory coupled to the one or more processors andconfigured to store instructions, which, when executed by the one ormore processors, cause the one or more processors to perform operationscomprising: detecting, by the touch screen, a tap and hold gesture inputdirected to a media capture affordance displayed at a first location ona graphical user interface presented on the touch screen of the mediacapture device; responsive to the tap and hold gesture input, initiatinga media capture session on the media capture device in an unlocked mediacapture session state; responsive to the touch screen detecting a firstlift gesture in which the tap and hold gesture input lifts from thefirst location on the graphical user interface during the media capturesession, terminating the media capture session; responsive to the touchscreen detecting a slide gesture input in which the media captureaffordance slides from the first location to a second location on thegraphical user interface during the media capture session, changing themedia capture affordance to a media capture lock affordance; andresponsive to the touch screen detecting a second lift gesture in whichthe slide gesture input lifts from the graphical user interface at thesecond location during the media capture session, transitioning themedia capture session into a locked media capture session state.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: a display screen; means for detecting atap and hold gesture input directed to a media capture affordancedisplayed at a first location on a graphical user interface presented ona display screen of the media capture device; means for, responsive tothe tap and hold gesture input, initiating a media capture session onthe media capture device in an unlocked media capture session state;means for, responsive to the media capture device detecting a first liftgesture in which the tap and hold gesture input lifts from the firstlocation on the graphical user interface during the media capturesession, terminating the media capture session; means for, responsive tothe media capture device detecting a slide gesture input in which themedia capture affordance slides from the first location to a secondlocation on the graphical user interface during the media capturesession, changing the media capture affordance to a media capture lockaffordance; and means for, responsive to the media capture devicedetecting a second lift gesture in which the slide gesture input liftsfrom the graphical user interface at the second location during themedia capture session, transitioning the media capture session into alocked media capture session state.

Particular embodiments disclosed herein may provide one or more of thefollowing advantages. A media capture lock affordance allows a user tolock and unlock a capture state of a media capture device using a simpleand intuitive touch gesture that can be applied by the user's finger(e.g., the user's thumb) while holding the media capture device in onehand.

The details of one or more implementations of the subject matter are setforth in the accompanying drawings and the description below. Otherfeatures, aspects and advantages of the subject matter will becomeapparent from the description, the drawings and the claims.

In accordance with some embodiments, a method is described. The methodcomprises: at a device with a display, a touch-sensitive surface, andone or more media capture components: displaying, on the display, afirst user interface element; detecting, via the touch-sensitivesurface, a touch input that begins at a location on the touch-sensitivesurface that corresponds to the first user interface element; and inresponse to detecting the touch input: in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets movement criteria and before athreshold amount of time has elapsed since the touch input was detected,capturing a first type of media; in accordance with a determination thatthe touch input is lifted from the touch-sensitive surface before thetouch input meets the movement criteria and after the threshold amountof time has elapsed since the touch input was detected, capturing asecond type of media that has a duration that is based on the durationof the touch input on the touch-sensitive surface; and in accordancewith a determination that the touch input meets the movement criteriaand includes movement in a first direction, starting to capture thesecond type of media and continuing to capture the second type of mediaafter detecting liftoff of the touch input from the touch-sensitivesurface.

In accordance with some embodiments, a non-transitory computer-readablestorage medium is described. The non-transitory computer-readablestorage medium stores one or more programs configured to be executed byone or more processors of an electronic device with a display, atouch-sensitive surface, and one or more media capture components, theone or more programs including instructions for: displaying, on thedisplay, a first user interface element; detecting, via thetouch-sensitive surface, a touch input that begins at a location on thetouch-sensitive surface that corresponds to the first user interfaceelement; and in response to detecting the touch input: in accordancewith a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaand before a threshold amount of time has elapsed since the touch inputwas detected, capturing a first type of media; in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethreshold amount of time has elapsed since the touch input was detected,capturing a second type of media that has a duration that is based onthe duration of the touch input on the touch-sensitive surface; and inaccordance with a determination that the touch input meets the movementcriteria and includes movement in a first direction, starting to capturethe second type of media and continuing to capture the second type ofmedia after detecting liftoff of the touch input from thetouch-sensitive surface.

In accordance with some embodiments, a transitory computer-readablestorage medium is described. The transitory computer-readable storagemedium stores one or more programs configured to be executed by one ormore processors of an electronic device with a display, atouch-sensitive surface, and one or more media capture components, theone or more programs including instructions for: displaying, on thedisplay, a first user interface element; detecting, via thetouch-sensitive surface, a touch input that begins at a location on thetouch-sensitive surface that corresponds to the first user interfaceelement; and in response to detecting the touch input: in accordancewith a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaand before a threshold amount of time has elapsed since the touch inputwas detected, capturing a first type of media; in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethreshold amount of time has elapsed since the touch input was detected,capturing a second type of media that has a duration that is based onthe duration of the touch input on the touch-sensitive surface; and inaccordance with a determination that the touch input meets the movementcriteria and includes movement in a first direction, starting to capturethe second type of media and continuing to capture the second type ofmedia after detecting liftoff of the touch input from thetouch-sensitive surface.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: a display; a touch-sensitive surface;one or more media capture components; one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:displaying, on the display, a first user interface element; detecting,via the touch-sensitive surface, a touch input that begins at a locationon the touch-sensitive surface that corresponds to the first userinterface element; and in response to detecting the touch input: inaccordance with a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaand before a threshold amount of time has elapsed since the touch inputwas detected, capturing a first type of media; in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethresh-old amount of time has elapsed since the touch input wasdetected, capturing a second type of media that has a duration that isbased on the duration of the touch input on the touch-sensitive surface;and in accordance with a determination that the touch input meets themovement criteria and includes movement in a first direction, startingto capture the second type of media and continuing to capture the secondtype of media after detecting liftoff of the touch input from thetouch-sensitive surface.

In accordance with some embodiments, an electronic device is described.The electronic device comprises: a display; a touch-sensitive surface;one or more media capture components; means for displaying, on thedisplay, a first user interface element; means for detecting, via thetouch-sensitive surface, a touch input that begins at a location on thetouch-sensitive surface that corresponds to the first user interfaceelement; and means for, responsive to detecting the touch input: inaccordance with a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaand before a threshold amount of time has elapsed since the touch inputwas detected, capturing a first type of media; in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethreshold amount of time has elapsed since the touch input was detected,capturing a second type of media that has a duration that is based onthe duration of the touch input on the touch-sensitive surface; and inaccordance with a determination that the touch input meets the movementcriteria and includes movement in a first direction, starting to capturethe second type of media and continuing to capture the second type ofmedia after detecting liftoff of the touch input from thetouch-sensitive surface.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for performing gesture-dependent media capture, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother methods for performing gesture-dependent media capture.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6H illustrate operation of a media capture lock affordance,according to an embodiment.

FIG. 7 is a flow diagram of an animation process for the media capturelock affordance shown in FIGS. 6A-6H, according to an embodiment.

FIG. 8 illustrates an example device architecture of a media capturedevice implementing the media capture lock affordance described inreference to FIGS. 1-2, according to an embodiment.

FIGS. 9A-9P illustrate exemplary user interfaces for performinggesture-dependent media capture in accordance with some embodiments.

FIGS. 10A-10F illustrate exemplary user interfaces for performinggesture-dependent media capture in accordance with some embodiments.

FIGS. 11A-11B is a flow diagram for performing gesture-dependent mediacapture in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for performing gesture-dependent media capture. Suchtechniques can reduce the cognitive burden on a user who uses a deviceto capture media, thereby enhancing productivity. Further, suchtechniques can reduce processor and battery power otherwise wasted onredundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6H illustrate exemplary user interfaces forperforming gesture-dependent media capture. FIG. 7 is a flow diagramillustrating methods of performing gesture-dependent media capture inaccordance with some embodiments. The user interfaces in FIGS. 6A-6H areused to illustrate the processes described below, including theprocesses in FIG. 7. FIGS. 9A-10F illustrate exemplary user interfacesfor performing gesture-dependent media capture. FIGS. 11A-11B is a flowdiagram illustrating methods of performing gesture-dependent mediacapture in accordance with some embodiments. The user interfaces in FIG.9A-10F are used to illustrate the processes described below, includingthe processes in FIGS. 11A-11B.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 and1100 (FIGS. 7 and 11). A computer-readable storage medium can be anymedium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6H illustrate exemplary user interfaces for performinggesture-dependent media capture, in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIG. 7.

Example Media Lock Affordance

This disclosure relates to media recording functionality of a mediacapture device that locks a media capture affordance on a graphical userinterface (GUI) into a locked media capture state for continuous mediacapture. In an embodiment, to initiate a media capture session of amedia clip (e.g., a video clip, audio clip), the user taps and holds themedia capture affordance (e.g., a virtual recording button). As long asthe user holds their touch on the media capture affordance, the mediacontinues to be captured by the media capture device. If the userremoves their touch during the media capture session, the media capturesession terminates. If the user maintains their touch on the mediacapture affordance while making a sliding gesture with their finger, themedia capture affordance visually changes to a locked media captureaffordance and the media capture session is maintained, resulting incontinuous recording of the media. In an embodiment, the locked mediacapture affordance moves down below the user's finger so that it is notobscured by the user's finger. The user can remove their finger from thelocked media capture affordance and the media capture session will bemaintained until the user taps the locked state capture button, whichthen terminates the media capture session.

FIGS. 6A-6H illustrate operation of a media capture lock affordance,according to an embodiment. Referring to FIG. 6A, media capture device600 is presenting GUI 601 on a display screen. GUI 601 includes mediacapture affordance 602. Media capture device 600 is shown in thisexample embodiment as a smartphone. Media capture device 600, however,can be any electronic device capable of capturing media, includingtablet computers, wearable computers, digital cameras, video recordersand audio recording devices. In some embodiments, media capture device600 includes one or more features of devices 100, 300, or 500. Mediacapture affordance 602 can have any desired shape, size or color. In theexample shown, media capture affordance 602 is an oval shape button. GUI601 also includes a display area for displaying live media and playingback captured media. Media can be any type of media that can becaptured, including video, still images and audio or any combinationthereof.

Referring to FIG. 6B, a user taps and holds 603 (shown as a dashedcircle) media capture affordance 602 with their finger (e.g., theirthumb while holding media capture device 600) to initiate a mediacapture session in an “unlocked” state. During the media capturesession, an embedded video camera and/or one or more microphones capturemedia (e.g., capture video and audio). The media capture session is“unlocked” meaning that if the user lifts their finger from mediacapture affordance 602 (lifts their finger off the display screen), themedia capture session terminates, and the media is stored on mediacapture device 600 (e.g., stored in cache memory). Visual directionindicator 604 a (e.g., an arrow head) is displayed on GUI 601 toindicate a direction in which the user may slide their finger totransition the media capture session into a “locked” state. While in the“locked” state, the media is continuously captured without interruption.For example, video and audio will continue to record and still imageswill be taken in “burst” mode. Text is also displayed on GUI 601 thatinstructs the user to “slide up for continuous recording.”

In some embodiments, additional affordances (not shown) are included onGUI 601 for allowing the user to playback the captured media(hereinafter also referred to as a “media clip”), and order, filter, addemoji, animated icons and titles to the media clip. Other affordancesallow the user to share the media clips indirectly with socialnetworking websites and directly with friends and family through variouscommunication means (e.g., instant messaging, email, tweeting). In theembodiment shown, a navigation bar is located under the media displayarea that allows the user select an operation mode such as Camera,Library and Posters.

Referring to FIG. 6C, shows the user's slide gesture input resulting inmedia capture affordance 602 sliding up toward the media capture area.Note that during a slide gesture input the user's finger does not breakcontact with the display screen.

Referring to FIGS. 6D-6G, when the user slides media capture affordance602 up a predetermined distance, media capture affordance 602 changes ormorphs into media capture lock affordance 605 to visually indicate a“locked” state, as shown in FIG. 6F. The text below the media displayarea also changes to instruct the user how to exit the “locked” statesuch as, for example, “tap to stop recording.” Media capture lockaffordance 605 can be any size, shape or color. In the example shown,media capture lock affordance 605 is a square button. After the changeor morph from media capture affordance 602 to media capture lockaffordance 605, if the user lifts their finger and breaks contact withthe display screen, the media capture session enters the “locked” state.In the “locked” state the media capture session continues with the mediacapture until the user taps 606 media capture lock affordance 605 (FIG.6G), in which case the media capture session terminates. In analternative embodiment, visual direction indicator 604 a can be replacedwith button track 604 b (FIG. 6H) to show the user the distance the usershould slide media capture affordance 602 to enter the “locked” state.

In other embodiments, multiple taps can be used instead of a single tap.The direction of the slide gesture input can be in any direction on GUI601, including up, down, right and left. A sound effect can be played insync with the tap and slide gesture, such as a “click” sound effect toindicate when the media capture session is locked and unlocked. In anembodiment, force feedback (e.g., a vibration) can be provided by ahaptic engine to indicate when the media capture session is locked andunlocked. Affordances 602, 606 can be placed at any desired location onGUI 601, and can change location, size and/or shape in response to theorientation of media capture device 600, such as portrait and landscapeorientations. In an embodiment, the user can enter or exit a lockedmedia capture state using a voice command, which is processed by aspeech detection/recognition engine implemented in media capture device600.

Example Processes

FIG. 7 is a flow diagram of an animation process for the media capturelock affordance shown in FIGS. 6A-6H, according to an embodiment.Process 700 can be implemented using the device architecture 800described in reference to FIG. 8. Process 700 is performed at a device(e.g., 100, 300, 500, 800). Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

Process 700 begins by receiving a tap and hold gesture input directed toa media capture affordance at a first location of a GUI presented on adisplay device of a media capture device (701). The media captureaffordance can be any size, shape or color. The first location can beany desired location on the GUI. Responsive to the tap and hold gestureinput, process 700 initiates a media capture session on the mediacapture device, where the media capture session is initiated in an“unlocked” state (702). Responsive to a first lift gesture at the firstlocation, process 700 terminates the media capture session (703).

Responsive to a slide gesture input from the first location to a secondlocation on the GUI, process 700 changes the media capture affordance toa media capture lock affordance (704). The media capture lock affordancecan be any size, shape or color. The second location can be any desiredlocation on the GUI except the first location. The slide gesture can bein any desired direction including up, down, left and right.

Responsive to detecting a second lift gesture at the second location,process 700 transitions the media capture session from an unlocked stateinto a locked state (705). In a locked state, the media capture devicewill capture media continuously, until the user taps the media capturelock affordance to terminate the media capture session. In anembodiment, the user can tap anywhere on the GUI to terminate the mediacapture session after the second lift gesture, or press a mechanicalbutton on the media capture device (e.g., a home button on asmartphone).

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, method 700 optionally includesone or more of the characteristics of the various methods describedbelow with reference to method 1100. For brevity, these details are notrepeated below.

Exemplary Mobile Device Architecture

FIG. 8 illustrates an example media capture device architecture 800 of amobile device implementing the media capture lock affordance describedin reference to FIGS. 6 and 7. Architecture 800 can include memoryinterface 802, one or more data processors, image processors and/orprocessors 804 and peripherals interface 806. Memory interface 802, oneor more processors 804 and/or peripherals interface 806 can be separatecomponents or can be integrated in one or more integrated circuits. Thevarious components in architecture 800 can be coupled by one or morecommunication buses or signal lines.

Sensors, devices and subsystems can be coupled to peripherals interface806 to facilitate multiple functionalities. For example, one or moremotion sensors 810, light sensor 812 and proximity sensor 814 can becoupled to peripherals interface 806 to facilitate motion sensing (e.g.,acceleration, rotation rates), lighting and proximity functions of themobile device. Location processor 815 can be connected to peripheralsinterface 806 to provide geopositioning. In some implementations,location processor 815 can be a GNSS receiver, such as a GlobalPositioning System (GPS) receiver chip. Electronic magnetometer 816(e.g., an integrated circuit chip) can also be connected to peripheralsinterface 806 to provide data that can be used to determine thedirection of magnetic North. Electronic magnetometer 816 can providedata to an electronic compass application. Motion sensor(s) 810 caninclude one or more accelerometers and/or gyros configured to determinechange of speed and direction of movement of the mobile device.Barometer 817 can be configured to measure atmospheric pressure aroundthe mobile device.

Camera subsystem 820 and an optical sensor 822, e.g., a charged coupleddevice (CCD) or a complementary metal-oxide semiconductor (CMOS) opticalsensor, can be utilized to facilitate camera functions, such ascapturing photographs and recording video clips.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 824, which can include radio frequency (RF)receivers and transmitters (or transceivers) and/or optical (e.g.,infrared) receivers and transmitters. The specific design andimplementation of the communication subsystem 824 can depend on thecommunication network(s) over which a mobile device is intended tooperate. For example, architecture 800 can include communicationsubsystems 824 designed to operate over GSM networks, GPRS networks,EDGE networks, a Wi-Fi™ or Wi-Max™ networks and Bluetooth™ networks. Inparticular, the wireless communication subsystems 824 can includehosting protocols, such that the mobile device can be configured as abase station for other wireless devices.

Audio subsystem 826 can be coupled to a speaker 828 and a microphone 830to facilitate voice-enabled functions, such as voice recognition, voicereplication, digital recording and telephony functions. Audio subsystem826 can be configured to receive voice commands from the user.

I/O subsystem 840 can include touch surface controller 842 and/or otherinput controller(s) 844. Touch surface controller 842 can be coupled toa touch surface 846 or pad. Touch surface 846 and touch surfacecontroller 842 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared and surfaceacoustic wave technologies, as well as other proximity sensor arrays orother elements for determining one or more points of contact with touchsurface 846. Touch surface 846 can include, for example, a touch screen.I/O subsystem 840 can include a haptic engine or device for providinghaptic feedback (e.g., vibration) in response to commands from aprocessor.

Other input controller(s) 844 can be coupled to other input/controldevices 848, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of speaker 828 and/or microphone 830. Touch surface 846 or othercontrollers 844 (e.g., a button) can include, or be coupled to,fingerprint identification circuitry for use with a fingerprintauthentication application to authenticate a user based on theirfingerprint(s).

In one implementation, a pressing of the button for a first duration maydisengage a lock of the touch surface 846; and a pressing of the buttonfor a second duration that is longer than the first duration may turnpower to the mobile device on or off. The user may be able to customizea functionality of one or more of the buttons. The touch surface 846can, for example, also be used to implement virtual or soft buttonsand/or a virtual touch keyboard.

In some implementations, the mobile device can present recorded audioand/or video files, such as MP3, AAC and MPEG files. In someimplementations, the mobile device can include the functionality of anMP3 player. Other input/output and control devices can also be used.

Memory interface 802 can be coupled to memory 850. Memory 850 caninclude high-speed random access memory and/or non-volatile memory, suchas one or more magnetic disk storage devices, one or more opticalstorage devices and/or flash memory (e.g., NAND, NOR). Memory 850 canstore operating system 852, such as iOS, Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks. Operatingsystem 852 may include instructions for handling basic system servicesand for performing hardware dependent tasks. In some implementations,operating system 852 can include a kernel (e.g., UNIX kernel).

Memory 850 may also store communication instructions 854 to facilitatecommunicating with one or more additional devices, one or more computersand/or one or more servers, such as, for example, instructions forimplementing a software stack for wired or wireless communications withother devices. Memory 850 may include graphical user interfaceinstructions 856 to facilitate graphic user interface processingdescribed in reference to FIGS. 6 and 7; sensor processing instructions858 to facilitate sensor-related processing and functions; phoneinstructions 860 to facilitate phone-related processes and functions;electronic messaging instructions 862 to facilitate electronic-messagingrelated processes and functions; web browsing instructions 864 tofacilitate web browsing-related processes and functions; mediaprocessing instructions 866 to facilitate media processing-relatedprocesses and functions; GNSS/Location instructions 868 to facilitategeneric GNSS and location-related processes and instructions; camerainstructions 870 to facilitate camera-related processes and functionsdescribed in reference to FIGS. 6 and 7; and other application 872instructions. The memory 850 may also store other software instructions(not shown), such as security instructions, web video instructions tofacilitate web video-related processes and functions and/or web shoppinginstructions to facilitate web shopping-related processes and functions.In some implementations, the media processing instructions 866 aredivided into audio processing instructions and video processinginstructions to facilitate audio processing-related processes andfunctions and video processing-related processes and functions,respectively.

In an embodiment, the taps, slide and lift gestures described inreference to FIGS. 6 and 7 are detected using a touch event modelimplemented in software on media capture device 800. An example touchevent model is described in U.S. Pat. No. 8,560,975, entitled “TouchEvent Model,” issued on Oct. 15, 2013, which patent is incorporated byreference herein in its entirety.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. Memory 850 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the mobile device may be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

The described features can be implemented advantageously in one or morecomputer programs that are executable on a programmable system includingat least one programmable processor coupled to receive data andinstructions from, and to transmit data and instructions to, a datastorage system, at least one input device, and at least one outputdevice. A computer program is a set of instructions that can be used,directly or indirectly, in a computer to perform a certain activity orbring about a certain result. A computer program can be written in anyform of programming language (e.g., SWIFT, Objective-C, C#, Java),including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, component,subroutine, a browser-based web application, or other unit suitable foruse in a computing environment.

Suitable processors for the execution of a program of instructionsinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors orcores, of any kind of computer. Generally, a processor will receiveinstructions and data from a read-only memory or a random-access memoryor both. The essential elements of a computer are a processor forexecuting instructions and one or more memories for storing instructionsand data. Generally, a computer will also include, or be operativelycoupled to communicate with, one or more mass storage devices forstoring data files; such devices include magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; andoptical disks. Storage devices suitable for tangibly embodying computerprogram instructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such as EPROM,EEPROM, and flash memory devices; magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, ASICs (application-specific integrated circuits).

To provide for interaction with a user, the features can be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor or a retina display device fordisplaying information to the user. The computer can have a touchsurface input device (e.g., a touch screen) or a keyboard and a pointingdevice such as a mouse or a trackball by which the user can provideinput to the computer. The computer can have a voice input device forreceiving voice commands from the user.

The features can be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system can be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks include, e.g., a LAN, a WAN, and thecomputers and networks forming the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

A system of one or more computers can be configured to performparticular actions by virtue of having software, firmware, hardware, ora combination of them installed on the system that in operation causesor cause the system to perform the actions. One or more computerprograms can be configured to perform particular actions by virtue ofincluding instructions that, when executed by data processing apparatus,cause the apparatus to perform the actions.

One or more features or steps of the disclosed embodiments may beimplemented using an Application Programming Interface (API). An API maydefine on or more parameters that are passed between a callingapplication and other software code (e.g., an operating system, libraryroutine, function) that provides a service, that provides data, or thatperforms an operation or a computation. The API may be implemented asone or more calls in program code that send or receive one or moreparameters through a parameter list or other structure based on a callconvention defined in an API specification document. A parameter may bea constant, a key, a data structure, an object, an object class, avariable, a data type, a pointer, an array, a list, or another call. APIcalls and parameters may be implemented in any programming language. Theprogramming language may define the vocabulary and calling conventionthat a programmer will employ to access functions supporting the API. Insome implementations, an API call may report to an application thecapabilities of a device running the application, such as inputcapability, output capability, processing capability, power capability,communications capability, etc.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to a subcombination or variation of a sub combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

FIGS. 9A-9P and 10A-10F illustrate exemplary user interfaces forperforming gesture-dependent media capture, in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 11A-11B.

FIG. 9A illustrates an exemplary media capture user interface 904. Insome embodiments, device 900 includes one or more features of devices100, 300, or 500. In this example, device 900 includes a touch screendisplay 902 that displays media capture interface 904. In someembodiments, a media capture interface is used to capture one or moretypes of media responsive to user input (e.g., touch input). Forexample, a media capture interface can be an graphical user interfacethat is usable to capture one or more of: still images, videos (e.g.,including audio), and sequences of images (e.g., burst image capture).Media capture interface 904 includes a viewfinder area 906 that includesa depiction of a scene being acquired by a media capture component suchas an image sensor (e.g., optical sensor 164), for example, that passesa view of the scene through for display at the media capture interface(e.g., so that the user can decide an appropriate time to capture amedia item). Media capture interface 904 also includes a mode selector908, for example, which can be used (e.g., via touch input, a swipeinput) to change a media capture mode (e.g., from “Photo” to “Video”, orto “Panoramic”, “Time-Lapse”, “Slow Motion”, or the like). Media captureinterface 904 also includes a media capture affordance 910. A mediacapture affordance can also be referred to as a “shutter” or “shutteraffordance,” or the like.

In some embodiments, a touch input (e.g., a tap gesture, also referredto as a tap) on a media capture affordance causes the device to capturea media item (e.g., in accordance with the current media capture mode).For example, in the example shown in FIG. 9A, the current media capturemode is “Photo”, so the user can expect device 900 to capture a stillimage in response to a tap on media capture affordance 910. Mediacapture interface 904 also includes a camera selector affordance 912,which can be used to change (e.g., responsive to user input) the imagesensor of device 900 being used to capture media (e.g., front facingcamera, rear facing camera). Media capture interface 904 also includes alast captured media item area 914 that displays a preview of a lastcaptured media item (e.g., a thumbnail, a single frame of a video). Insome embodiments, in response to touch input associated with a lastcapture media item area (e.g., 914), the device (e.g., 900) displays oneor more recently capture media items, a plurality of media items (e.g.,a camera roll), and/or a media library.

As noted above, a device (e.g., 900) typically responds to user input ona media capture affordance (e.g., 910) based on the current mediacapture mode. Described herein are techniques for gesture-dependentcapture of media. The gesture-dependency can cause media of differenttypes to be captured, based on the particular gesture used. Theparticular gestures usable to capture media can have differentproperties based on user input characteristics (e.g., duration,movement, and/or various combinations thereof). As will be illustratedin the examples below of FIGS. 9A-9P, the type of media captured doesnot necessarily correspond to the media capture mode active when thetouch input is received.

Notably, an input characteristic box 901 is included throughout FIGS.9A-9P and indicates characteristics of a touch input (e.g., detected byelectronic device 900) in the corresponding figure and is provided as avisual representation of the touch input characteristics (e.g., inmemory of device 900) in the respective example scenario depicted ineach respective figure. The input characteristics associated with atouch input can be used by a device (e.g., 900) to determine whether atouch input satisfies criteria for being considered a particular gesture(e.g., which can cause a media capture-related action to be performed).Input characteristic box 901 is provided merely as a visual aid for easeof the reader's understanding, and is not necessarily displayed by adevice (e.g., 900). Additionally, unless otherwise noted in a figure orherein, input characteristic box 901 indicates characteristics of atouch input after device 900 receives the depicted touch input (e.g.,920 in FIG. 9B) in the respective figure, and before such input ceasesto be detected (e.g., liftoff of the touch input).

FIGS. 9A-9B illustrate capture of a first type of media item. In theexample depicted in FIGS. 9A-9B, device 900 captures a first type ofmedia item that corresponds to the current media capture mode (e.g.,“Photo”). In FIG. 9B, device 900 receives user input 920, which is atouch input at a location on touch screen display 902 corresponding tomedia capture affordance 910. As shown in input characteristic box 901of FIG. 9B, the user input 920 (also referred to as touch input 920) hasnot met movement criteria (MOVEMENT CRITERIA: NOT MET), and has not beendetected for longer than a threshold amount of time (THRESHOLD TIME: NOTPASSED). In this example, device 900 ceases to detect touch input 920(e.g., due to liftoff of the input) before the movement criteria hasbeen met and before the threshold time has passed. Thus, in thisexample, touch input 920 is a tap input gesture. FIG. 9C illustratesdevice 900 after liftoff of touch input 920. In FIG. 9C, media captureinterface 904 returns to the same state as shown in FIG. 9A, howeverlast captured media item area 914 now includes a representation of thecurrent scene shown in viewfinder area 906, illustrating that device 900captured a media item. In this example, device 900 captured a stillimage (e.g., an exemplary first type of media). In some embodiments,device 900 captures a second type of media item, in addition to thefirst type of media item, in response to a user input that did not meetmovement criteria and that was not detected for more than a thresholdtime (e.g., a tap input). In some embodiments, the second type of mediahas a duration that is independent of the duration of the touch input.For example, device 900 can additionally (or instead) capture a videoclip (e.g., including audio) of a fixed duration (e.g., 3 seconds long)or variable duration (e.g., between 2 to 5 seconds long) regardless ofthe duration of the touch input (e.g., 0.5 seconds).

FIGS. 9D-9F illustrate capture of a second type of media item. In theexample depicted in FIGS. 9D-9F, device 900 captures a second type ofmedia item (e.g., video) that does not correspond to the current mediacapture mode (e.g., “Photo”) using a touch input that does not satisfymovement criteria, but that does satisfy time criteria (e.g., isdetected for more than a threshold amount of time). In FIG. 9D, device900 receives user input 930, which is a touch input at a location ontouch screen display 902 corresponding to media capture affordance 910.As shown in input characteristic box 901 of FIG. 9D, the user input 930has not met movement criteria (MOVEMENT CRITERIA: NOT MET), and has notbeen detected for longer than a threshold amount of time (THRESHOLDTIME: NOT PASSED).

FIG. 9E illustrates device 900 continuing to detect touch input 930until after the threshold time has passed, however before the movementcriteria has been met. Thus, input characteristic box 901 of FIG. 9Eshows that the user input 930 has not met movement criteria (MOVEMENTCRITERIA: NOT MET), but has been detected for longer than a thresholdamount of time (THRESHOLD TIME: PASSED). Thus, in this example, touchinput 930 is a tap and hold input gesture (e.g., a tap that is held fora threshold amount of time). In response to touch input 930 beingdetected for more than a threshold amount of time, device 900 beginscapturing (e.g., recording) a video (e.g., an exemplary second type ofmedia). As shown in FIG. 9E, device 900 is currently capturing a video.In this example, during video capture, an elapsed time of the video isshown (00:00:08, or 8 seconds), and media capture affordance 910 hasbeen replaced with a stop affordance 934. Additionally, in FIG. 9E,device 900 displays a media capture lock affordance 932 (e.g., replacingcamera selector affordance 912), which is discussed in more detailbelow.

FIG. 9F illustrates device 900 after liftoff of touch input 930. In FIG.9F, in response to liftoff of touch input 930, media capture interface904 returns to the same state as shown in FIG. 9D, however last capturedmedia item area 914 now includes a representation of the current sceneshown in viewfinder area 906, illustrating that device 900 captured amedia item. In this example, device 900 captured a video (e.g., anexemplary second type of media). In some embodiments, device 900captures a first type of media item, in addition to the second type ofmedia item, in response to a user input that did not meet movementcriteria but that was detected for more than a threshold time (e.g., atap and hold gesture, touch input 930). For example, in addition tocapturing a video, device 900 can additionally capture a still image. Insome embodiments, the second type of media (e.g., captured in responseto touch input 930) has a duration that is based on the duration of thetouch input (e.g., 930). For example, device 900 can capture a videoclip (e.g., including audio) that has a duration based on the durationthat touch input 930 was detected. Thus, if touch input 930 was detectedon touch screen display 902 for 8 seconds, the resulting captured secondtype of media can be an 8 second long video. In some embodiments, theduration of the second type of media is based on the touch inputduration, but video recording begins after the touch input is detectedfor more than the threshold duration. Thus, if the threshold duration is1 second and the touch input is detected for 8 seconds, the resultingvideo is 7 seconds (e.g., where liftoff causes the recording of video toend, which is then stored in a media library by device 900).

FIGS. 9G-9J illustrate using a gesture to begin capture of a second typeof media that continues after the gesture ceases to be detected. In theexample depicted in FIGS. 9G-9J, device 900 captures a second type ofmedia item (e.g., video) that does not correspond to the current mediacapture mode (e.g., “Photo”) using a touch input 940 that satisfiesmovement criteria (e.g., in a first direction) (and also satisfies timecriteria). In FIG. 9G, device 900 receives user input 940, which is atouch input at a location on touch screen display 902 corresponding tomedia capture affordance 910. As shown in input characteristic box 901of FIG. 9D, the user input 940 has not met movement criteria (MOVEMENTCRITERIA: NOT MET), and has not been detected for longer than athreshold amount of time (THRESHOLD TIME: NOT PASSED).

In the example in FIGS. 9G-9J, although touch input 940 is detected forlonger than a threshold duration, the satisfaction of the thresholdduration is not a requirement for transitioning the media capturesession into a locked media capture state. Rather, in this example, themovement criteria being satisfied is the only requirement. In someembodiments, a threshold amount of time may additionally be required tolock the media capture session.

FIG. 9H illustrates device 900 continuing to detect touch input 940until after the threshold time has passed, however before the movementcriteria has been met. Thus, input characteristic box 901 of FIG. 9Hshows that the user input 940 has not met movement criteria (MOVEMENTCRITERIA: NOT MET), but has been detected for longer than a thresholdamount of time (THRESHOLD TIME: PASSED). Similar to the example describeabove in FIGS. 9D-9F, in response to a touch input that is detected forlonger than a threshold period, device 900 has begun capturing (e.g.,recording) a video (e.g., an exemplary second type of media). In thisexample, touch input 940 is a touch input that is dragged from aninitial location of contact (e.g., location of 910). As used herein atouch input that is “dragged” is also referred to as a touch input that“slides.” In FIG. 9H, touch input 940 has been dragged to the right ofmedia capture affordance 910. As shown in FIG. 9H, device 900 iscurrently capturing a video. In this example, an elapsed time of thevideo is shown (00:00:08, or 8 seconds), and media capture affordance910 has been replaced with a stop affordance 934. A stop affordance isalso referred to herein as a “locked state capture button” (e.g., whenit replaces a media capture affordance during a locked media capturesession). In some embodiments, a stop affordance (e.g., 934) replaces amedia capture affordance (e.g., 910) in response to liftoff of the touchinput (e.g., that causes a media capture session to enter a locked mediacapture state). Additionally, in FIG. 9H, device 900 displays a mediacapture lock affordance 932 (e.g., replacing camera selector affordance912), which is discussed in more detail below.

Notably, the scenario depicted in FIG. 9H is similar to the scenario inFIG. 9E, except that the touch input in FIG. 9H (940) has moved to theright slightly, and the touch input in FIG. 9E (930) has not moved.Thus, because touch input 940 has not met the movement criteria, but hasbeen detected for longer than the threshold time, if touch input 940were to cease to be detected (e.g., due to liftoff of touch input 940)at the instant depicted in FIG. 9H, a similar result as that shown inFIG. 9F would occur—device 900 would capture a video having a durationbased on the duration that touch input 940 was detected. However, inthis example touch input 940 continues to be detected, as shown in FIGS.9I and 9J, discussed below.

In FIG. 9H, device 900 displays a touch input indicator 942 that is arepresentation of the current location of touch input 940. In thisexample, touch input indicator is displayed in response to movement ofthe touch input 940 (e.g., movement of the touch input away from thearea associated with media capture affordance 910 (FIG. 9G)/stopaffordance 934 (FIG. 9H)). Also depicted is a movement path indicator943, which is displayed between stop affordance 934 (or media capture910 if it had not been replaced by stop affordance 934) and mediacapture lock affordance 932. Touch input indicator 942 moves along theindicated movement path in response to dragging (also referred to as“sliding”) of touch input 940 (e.g., in one or either direction left orright).

Turning now to FIGS. 9I and 9J, they illustrate a technique forcontinuing capture of media after ceasing to detect a user input. Asdiscussed above with respect to FIGS. 9B-9C, a device optionallycaptures a first type of media in response to a user input (e.g.,gesture) that has certain characteristics (e.g., no movement, detectedfor less than a threshold time). As discussed above with respect toFIGS. 9D-9F, the device optionally captures a second type of media(e.g., video) that is based on a duration of a user input if the userinput has other characteristics (e.g., no movement (or movement notmeeting criteria), and is detected for more than a threshold time). Insome embodiments, the device continues to capture of the second type ofmedia to continue even after the touch input ceases to be detected.

In FIG. 9I, touch input 940 has moved further to the right and is now ata location that corresponds to media capture lock affordance 932. Inthis example, movement criteria is met when a touch input (e.g., 940) ismoved (e.g., dragged) from a location of the media capture affordance910 (e.g., at touch-down) (or from a location of a stop affordance(e.g., 934) that has replaced media capture affordance) to a location ofmedia capture lock affordance 932. In some embodiments, the devicedetermines whether movement criteria is met in response to the userinput ceasing to be detected (e.g., at time of liftoff of the touchinput). Thus, input characteristic box 901 of FIG. 9I shows that theuser input 940 will meet movement criteria if liftoff occurs at thecurrent location (MOVEMENT CRITERIA: MET (AT LIFTOFF)), and that thetouch input has been detected for longer than a threshold amount of time(THRESHOLD TIME: PASSED). As shown in FIG. 9I, movement indicator 942does not cover/obscure media capture lock affordance 932 while thecontact is at the corresponding location and continues to be detected.In some embodiments, a movement indicator (e.g., 942) covers/obscures amedia capture lock affordance (e.g., 932) while the contact is at thecorresponding location and continues to be detected. As shown in FIG.9I, media capture interface 904 remains in a video recording state—stopaffordance 934 continues to be displayed, and the elapsed time of thevideo capture continues to be displayed (00:00:10, or 10 seconds).

FIG. 9J illustrates device 900 after liftoff of touch input 940. Inresponse to ceasing to detect touch input 940, and because liftoff oftouch input 940 occurred after meeting the movement criteria (e.g.,liftoff on affordance 932), device 900 continues capturing the secondtype of media (e.g., video recording). Continuing to capture media isalso referred to herein as “maintaining” a media capture session. Inthis example, device 900 continues capturing the second type of mediabecause the media capture session (e.g., capturing of the video) wastransitioned from an unlocked media capture state to a locked mediacapture state. A media capture state is also referred to herein as a“media capture session state.” As used herein, a media capture sessionthat is in an unlocked media capture state is also referred to a mediacapture session that is “unlocked.” As used herein, a media capturesession that is in a locked media capture state is also referred to amedia capture session that is “locked.” In some embodiments, when amedia capture session is in a locked media capture state, the mediasession continues (e.g., after ceasing to detect a touch input gesturethat causes the media session to begin). As shown in FIG. 9J, mediacapture interface 904 remains in a video recording state—stop affordance934 continues to be displayed, and the elapsed time of the video capturecontinues to be displayed (00:00:12, or 12 seconds) (e.g., andprogresses further as more time passes during capture). Also shown inFIG. 9J, device 900 displays image capture affordance 944, which can beused to capture a first type of media (e.g., still image, and/or fixedduration clip) while continuing to capture a second type of media (e.g.,video). In this example, device 900 continues capturing a video (e.g.,an exemplary second type of media).

In some embodiments, device 900 captures a first type of media item, inaddition to the second type of media item, in response to a user inputthat met movement criteria and that was detected for more than athreshold time. For example, in addition to capturing a video, device900 can additionally capture a still image in response to touch input940. In some embodiments, the still image is discarded. For example, afirst type of media (e.g., still image) can be taken in response totouch-down of a touch input, but the device can discard the first typeof media if a second type of media is captured (e.g., touch inputcontinues for threshold time, or meets movement criteria).

In some embodiments, the device determines whether movement criteria ismet while the user input continues to be detected. For example, device900 can determine that touch input 940 met the movement criteria uponreaching a particular location, such as the location of media capturelock affordance 932 in FIG. 9I. In such example, in response to the userinput meeting the movement criteria, the device can cause the currentmedia capture session to transition to a locked media capture state(e.g., as shown in FIG. 9J) without first requiring liftoff (e.g., evenwhen touch input 940 is still detected). Thus, device 900 can continuecapture of the second type of media despite additional movement of thetouch input 940 (e.g., to a location as shown in FIG. 9H, back in thedirection of media capture affordance 910) and liftoff at a locationother than that of media capture lock affordance 932. In someembodiments, liftoff (e.g., of touch input 940) on media captureaffordance (e.g., 910) or on a stop affordance (e.g., 934) causes thedevice (e.g., 900) to cease capture of media (e.g., media capture doesnot continue after liftoff).

In some embodiments, the movement criteria is met if the touch input isdragged toward a media capture lock affordance (e.g., 932) by at least apredetermined amount (e.g., percentage, fixed distance). For example, iftouch input 940 drags movement indicator 942 at least 50% of thedistance between the location of media capture affordance 910 in FIG. 9G(e.g., same location as stop affordance 934 in FIG. 9H) and mediacapture lock affordance 932, then the movement criteria can be met(e.g., immediately, or upon liftoff). This is depicted in the examplesillustrated in FIGS. 10A-10F, which are discussed in more detail below.

In some embodiments, the movement criteria requires movement in aparticular direction (e.g., right, left, down, up) (e.g., in order to bemet). For example, FIGS. 9G-9J illustrate movement to the right (ofmedia capture affordance 910) being required to meet the movementcriteria. In some embodiments, movement criteria is satisfied bymovement in one or more directions (e.g., movement to the left or rightcan satisfy movement criteria).

FIG. 9K illustrates an exemplary technique for ceasing to capture asecond type of media while a media session is in a locked media capturestate. Because media continues being captured upon liftoff of touchinput 940, a touch input 950 on stop affordance 934 can be used to causedevice 900 to cease to capture of a video. For example, in response totouch input 950, device 900 can cease to record a video, and displaymedia capture interface 904 as shown in FIG. 9F (e.g., depicting nothingcurrently being recorded).

FIG. 9L illustrates an exemplary technique for capturing a first type ofmedia while a media session is in a locked media capture state. In FIG.9L, device 900 receives user input 960 on image capture affordance 944,which can be used to cause device 900 to capture a first type of media(e.g., still image, and/or fixed duration clip) while recording a secondtype of media (e.g., video). In this example, device 900 continuescapturing a video (e.g., an exemplary second type of media) after touchinput 960. In response to touch input 960, device 900 captures a stillimage from a video frame (e.g., including storing the still image in amedia library).

FIGS. 9M-9P illustrate capture of a sequence of the first type of mediaitem using a touch input gesture. In the example depicted in FIGS.9M-9P, device 900 captures a sequence of the first type of media item(e.g., still images) using a touch input that satisfies a secondmovement criteria. In some embodiments, the device determines whether auser input (e.g., touch input) meets one or more different movementcriteria (e.g., a first movement criteria and a second movementcriteria). For example, an exemplary first movement criteria can be themovement criteria discussed above with respect to FIGS. 9B-9K, wheremeeting the criteria causes the device to change a media capture sessionto the locked media capture state. In some embodiments, meeting a secondmovement criteria causes device 900 to take a different media captureaction (e.g., different than what is taken in response to the firstmovement criteria being met). In this example, device 900 performs aburst media capture in response to detecting a touch input that meets asecond movement criteria, discussed in more detail below.

In FIG. 9M, device 900 receives user input 970, which is a touch inputat a location on touch screen display 902 corresponding to media captureaffordance 910. As shown in input characteristic box 901 of FIG. 9D, theuser input 970 has not met movement criteria (MOVEMENT CRITERIA: NOTMET), and has not been detected for longer than a threshold amount oftime (THRESHOLD TIME: NOT PASSED).

FIG. 9N illustrates device 900 continuing to detect touch input 970until after the threshold time has passed, and after movement criteriahas been met. Thus, input characteristic box 901 of FIG. 9H shows thatthe user input 940 has not met movement criteria (MOVEMENT CRITERIA:MET), but has been detected for longer than a threshold amount of time(THRESHOLD TIME: PASSED). In the example in FIG. 9N, the movementcriteria that has been met is a second movement criteria. In thisexample, the second movement criteria is different from the (first)movement criteria described above with respect to FIGS. 9B-9K. In thisexample, the second movement criteria includes a threshold amount (e.g.,any amount, a minimum amount) of movement in a second direction. In theexample in FIG. 9N, the touch input 970 has moved in the seconddirection (e.g., to the left), different than a first direction (e.g.,right), by a minimum amount (e.g., a minimum amount of pixels). Inresponse to detecting that touch input 970 satisfies the second movementcriteria in the second direction, device 900 begins capturing a sequenceof media items of the first type of media item (e.g., begins capturingimages in a “burst” image capture mode). In this example, the device 900continues capturing the sequence of media items until ceasing to detectthe touch input 970. In some embodiments, the device enters a lockedmedia capture state while capturing the sequence of media items. Forexample, device 900 optionally provides the ability to lock the mediacapture session into the burst mode, so that the burst shootingcontinues upon liftoff of the touch input 970, similar to as describedabove with respect to video in FIGS. 9G-9J. Similar to as describedabove, the burst mode can be locked based on a touch input meeting oneor more movement criteria (e.g., a third movement criteria).

It should be noted that the description of the details of the firstmovement criteria and of the second movement criteria are not intendedto be exclusive to either, or to limit the properties of either (e.g.,in implementations of the techniques herein that differ from theexamples used herein). Thus, the specific details described with respectto a specific movement criteria herein are merely for example, and oneof skill appreciates that a movement criteria can have one or morecharacteristics of any movement criteria described herein.

As shown in FIG. 9N, while continuing to detect touch input 970, device900 continues to capture the sequence of media items. While continuingto capture the sequence of media items, device 900 displays a touchinput indicator 974 representing the location of touch input 970. Touchinput indicator 974 moves along an exemplary movement path indicator 975(FIG. 9O). Device 900 also displays a sequence count 972, whichindicates the number of media items that have been captured during theongoing (burst) media capture session capturing the sequence of mediaitems. As shown in FIG. 9N, one media item has been captured so farsince device 900 began capturing the current sequence (e.g., in responseto user input 970), as depicted by the number “1” in sequence count 972.

FIGS. 9O and 9P illustrate device 900 continuing to capture a sequenceof media items while a touch input continues to be detected. In FIG. 9O,touch input 970 continues to be detected, and has been dragged furtherto the left, and the sequence count 976 now reads “10” (e.g., 10 mediaitems of the first type have been captured). In FIG. 9O, touch inputindicator 974 moves along an exemplary movement path indicator 975(shown as a solid line). In some embodiments, the device (e.g., 900)moves (e.g., creates a duplicate, repositions, displays a new userinterface element containing) a sequence count in response to movementof the touch input. For example, in FIG. 9O, in response to the touchinput 970 moving toward (e.g., nearing, or reaching) a location of thesequence count 972 (of FIG. 9N), device 900 displays the number ofcaptured media items at a new location, in sequence count 976(corresponding to the original location of media capture affordance910). In some embodiments, the device (e.g., 900) ceases displaying thesequence count (e.g., 972) at the initial display location, inaccordance with moving the sequence count (e.g., to 976). In this way,device 900 prevents a dragged touch input from covering the sequencecount. In some embodiments, the sequence count does not move in responseto touch input movement. For example, the sequence count can bedisplayed at a single location (e.g., either the location of 972, 976,or another location) and not move in response to the touch input movingto the corresponding location. In some embodiments, the sequence countmoves a second time in response to additional movement. For example, ifthe touch input moves back to the location of sequence count 976, thesequence can move again (e.g., be displayed again as sequence count972).

In FIG. 9P, touch input 970 continues to be detected, and has beendragged further to the left, and the sequence count 976 now reads “20”(e.g., 20 media items of the first type have been captured). In someembodiments, the device (e.g., 900) ceases to capture the sequence ofmedia items in response to ceasing to detect the touch input. Forexample, if device 900 ceases to detect touch input 970 at the momentdepicted in FIG. 9P, capture of the sequence of media items would cease(e.g., after having captured 20 media items of the first type). In suchexample, in response to liftoff of touch input 970, device 900 candisplay a media capture interface 904 similar to as shown in FIG. 9F,with a last captured media item area 914 now including a representationof one of the 20 media items captured in the sequence of media items.

In some embodiments, an amount and/or speed of movement of a touch inputaffects a characteristic of the capturing of the sequence of media itemsof the first type. For example, a touch input with movement above athreshold speed (e.g., speed of movement on the touch screen display)can cause the rate of burst image capture to increase (e.g., to higherthan a similar touch input that moved at a slower speed) and/or remainat higher rate (e.g., than a similar touch input that moved at a slowerspeed). As another example, a touch input that moves a larger distancefrom an initial position (e.g., of 910) can cause a rate of burst imagecapture to be larger than a touch that moved a smaller distance.

FIGS. 10A-10F illustrate exemplary interfaces for causing a mediacapture session to transition from an unlocked media capture state to alocked media capture state. In particular, FIGS. 10A-10F illustrate anexemplary detail view of a touch input that interacts with one or moreaffordances to cause a media session to enter a locked media capturestate, as described above with respect to FIGS. 6A-6F and 9A-9P. Theinterfaces illustrated in FIGS. 10A-10F can be displayed by device 900(e.g., at one or more of the interfaces shown in FIGS. 9A-9P).

FIG. 10A depicts an exemplary media capture affordance 1000. Forexample, media capture affordance 1000 can include the samefunctionality as described above with respect to media captureaffordance 602 or 910.

In FIG. 10B, a user input 1002 (also referred to as touch input 1002) isreceived at a location associated with the media capture affordance 1000(e.g., the user input is detected by a device displaying affordance1000). In this example, similar to as described above with respect totouch input 930 of FIGS. 9D and 9E, touch input 1002 is detected forlonger than a threshold amount of time, and thus capture of a media(e.g., video) has begun (e.g., in response to the device detecting touchinput 1002, or in response to the touch input 1002 being detected forlonger than a threshold duration). As illustrated by the arrow in FIG.10B, touch input 1002 includes a movement component in a direction tothe right of media capture affordance 1000. Also shown in FIG. 10B, amedia capture lock affordance 1004 is now displayed to the right ofmedia capture affordance 1000. For example, media capture lockaffordance 1004 can include the same functionality as described abovewith respect to media capture lock affordance 932. FIG. 10B alsoillustrates movement path indicator 1005 connecting media captureaffordance 1000 and media capture lock affordance 1004, indicating amovement direction toward the media capture lock affordance 1004. Amovement path indicator is also referred to as a “visual directionindicator” as used herein.

In FIG. 10C, touch input 1002 has moved to the right slightly from FIG.10B, and in FIG. 10D the touch input 1002 has moved even farther to theright from FIG. 10C. In FIG. 10D, touch input indicator 1006 has not yetpassed lock distance marker 1008. Touch input indicator 1006 can includeone or more features of touch input indicator 942 described above. Insome embodiments, a lock distance marker (e.g., 1008) can be displayed(e.g., on a movement path indicator 1005) showing a location associatedwith (e.g., sufficient to meet) movement criteria. In FIG. 10D, lockdistance marker 1008 indicates the distance that meets movement criteriafor locking a media capture session state. In FIGS. 10C and 10D, thevideo continues being captured, as touch input 1002 continues to bedetected.

In FIG. 10E, touch input 1002 has moved to the right and has passed lockdistance marker 1008. In this example, the movement criteria does notrequire liftoff of the touch input (e.g., 1002) to satisfy the movementcriteria for causing a media capture session to transition to a lockedmedia capture state. Accordingly, in FIG. 10E, the media capture session(e.g., recording of video) has entered a locked media capture state. Forexample, as shown in FIG. 10F, video capture continues (e.g., stopaffordance 1010 is displayed, illustrating that a video is recording)after liftoff of touch input 1002 at the position in which it isdepicted in FIG. 10E. Also shown in FIG. 10E, media capture lockaffordance 1004 has been replaced with display of image captureaffordance 1012 (e.g., similar to image capture affordance 944), whichcan be used to capture media (e.g., a first type, such as a still image,and/or fixed duration clip) while recording a second type of media(e.g., video).

In FIG. 10F, the device has ceased to detect touch input 1002, butcontinues capturing media (e.g., recording a video), similar to asdescribed above with respect to FIG. 9J. In this example, liftoff oftouch input 1002 occurred while at the location depicted in FIG. 10E(e.g., before reaching the location associated with media capture lockaffordance 1004), but still resulted in the continuation of the mediacapture session because the movement of touch input 1002 moved (asrepresented by touch input indicator 1006) past lock distance marker1008. In some embodiments, the device does not display one or more of: atouch input indicator (e.g., 1006), a lock distance marker (e.g., 1008),and a movement path indicator (e.g., 1005). For example, with referenceto FIG. 10E, a device can display less than all (or none) of touch inputindicator 1006, lock distance marker 1008, and movement path indicator1005, but still perform that same action in response to liftoff asdescribed with respect to FIGS. 10E and 10F.

In the description above, touch inputs 920, 930, 940, 970, and 1002 arereferred to by different reference numerals. However, these touch inputsare intended to represent a plurality of potential gestures and/orresults that can occur based on whether the touch input ends up beingone or more gesture inputs. That is, each of the touch inputs 920, 930,940, 970, and 1002 represent different possible outcomes for a singletouch input. For example, touch inputs 920 and 930 begin in the samelocation and during the same device conditions and represent a commonstarting point for a touch input—however, one becomes a tap gesture(920) and one becomes a tap and hold gesture (930), and thus causedifferent media capture actions to be taken. Accordingly, the user canbe provided control of a plurality of media capture actions of a devicebased on which gesture the user performs with a touch input.

Additionally, the examples described above are illustrative and are notintended to be limiting with respect to the various combinations ofgestures, media actions, movement criteria, and threshold amounts oftime. For example, while video capture is described with respect tomovement in a rightward direction, burst media capture can be performedin response to movement to the right instead. Likewise, movement to theleft can result in capture of media of the first type (e.g., a stillimage) instead of resulting in burst media capture as described above.One of skill would recognize that various combinations of gestures,media actions, movement criteria, and threshold amounts of time can becombined and/or arranged in any combination to create a user interfacein accordance with the scope of this disclosure. All such interfaces areintended to be within the scope of this disclosure.

FIG. 11 is a flow diagram illustrating a method for performinggesture-dependent media capture using an electronic device in accordancewith some embodiments. Method 1100 is performed at a device (e.g., 100,300, 500, 800) with a display, a touch-sensitive surface, and one ormore media capture components (e.g., image sensors, cameras). Someoperations in method 1100 are, optionally, combined, the orders of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 1100 provides an intuitive way for performinggesture-dependent media capture. The method reduces the cognitive burdenon a user for performing media capture, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to perform media capture faster and moreefficiently conserves power and increases the time between batterycharges.

The electronic device (e.g., 600, 900) displays (1102) (e.g., at 601, at904), on the display (e.g., touch screen display 902), a first userinterface element (e.g., 910, 602, 1000). The electronic device detects(1104) (e.g., while displaying the first user interface element), viathe touch-sensitive surface (e.g., touch screen display 902), a touchinput (e.g., 603, 920, 930, 940, 970, 1002) that begins (e.g.,touch-down (finger-down) event of an object on a touch-sensitivesurface) at a location on the touch-sensitive surface that correspondsto the first user interface element (e.g., location of 910, location of602, location of 1000).

In response to detecting the touch input (1106), and in accordance witha determination that the touch input (e.g., 920) is lifted from thetouch-sensitive surface (e.g., 902) before the touch input meetsmovement criteria and before a threshold amount of time (e.g., 1 second)(e.g., an amount of time before video begins recording automatically)has elapsed since the touch input was detected (e.g., touch-down eventof touch input on the touch screen display 902), the electronic device(e.g., 600, 900) captures (1108) a first type of media (e.g., a singleimage, and/or a video having a fixed duration). For example, FIGS. 9B-9Cillustrate device 900 capturing a first type of media in accordance witha determination that exemplary touch input 920 (a tap input gesture) islifted from touch screen 902 before the touch input meets movementcriteria and before a threshold amount of time has elapsed since thetouch input was detected.

In some embodiments, a determination that the touch input (e.g., 920) islifted from the touch-sensitive surface (e.g., 902) before the touchinput meets movement criteria includes a determination that the touchinput is lifted before more than a threshold amount of movement (e.g.,movement sufficient to cause a media capture session to enter (e.g.,transition to) a locked media capture state from an unlocked mediacapture state) has been detected. For example, a threshold amount can bea predefined distance from touch-down location (e.g., a media captureaffordance), or a distance to a predefined region/area/location from atouch-down location (e.g., a media capture affordance). In someembodiments, a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaincludes a determination that the touch input is lifted: before thetouch input has moved outside of a first region (e.g., area, location)corresponding to a media capture affordance (e.g., 910, 602, 1000)and/or before the touch input has moved into a second region (e.g.,area, location) associated with capture of a second type of media thatcontinues after detecting liftoff. For example, the first region can bethe location of media capture icon affordance 910 (or stop affordance934 if it replaced 910 in accordance with beginning to record secondtype of media), while the second region can be the media capture lockaffordance 932. For further example, the second region can be a regionalong a movement path indicator (e.g., 974, 1005) (e.g., the region pasta certain point or distance from affordance 1000 or 1010, such as to theright of lock distance marker 1008 of FIG. 10E).

In some embodiments, capturing media includes one or more of: using theone or more media capture components (e.g., image sensors, cameras) torecord one or more images (e.g., a single image, a video comprising aseries of images), recording audio (e.g., while recording video) (e.g.,using one or more microphones), and storing a media item (e.g., arecording still image, a recorded video) in a media library. Forexample, capturing a media item can include beginning to record a videoclip, ceasing to record that video clip, and storing the video clip sothat it is associated with (e.g., accessible in) a media library (e.g.,a camera roll) associated with the device. As another example,“beginning to capture” can refer to the device beginning a recording ofa video. As another example, “ceasing to capture” can refer to thedevice ceasing (e.g., stopping the video recording) a recording of avideo. In some embodiments, the captured video resulting from “ceasingto capture” is stored in a media library (e.g., automatically inaccordance with the video ceasing to be recorded). In some embodiments,the device (e.g., 600, 900) captures the first type of media in responseto detecting touch-down of the touch input on the touch-sensitivesurface. In some embodiments, the device captures the first type ofmedia at any time during detection of the touch input (e.g., beginningwith touch-down) and liftoff of the touch input on the touch-sensitivesurface. In some embodiments, the device captures the first type ofmedia in response to liftoff of the touch input from the touch-sensitivesurface. In some embodiments, the first type of media is captured (orbegins being captured) before the touch-down of the touch input on thetouch-sensitive surface. For example, the device (e.g., 600, 900) can berecording before (e.g., in anticipation of) a touch input, and inresponse to the touch input captures one or more media items that werecaptured or began being captured (e.g., for a video) before the touchinput (e.g., 603, 920, 930, 940, 970, 1002) was actually detected by thedevice.

In response to detecting the touch input (1106), and in accordance witha determination that the touch input (e.g., 930) is lifted from thetouch-sensitive surface before the touch input meets the movementcriteria (e.g., before a threshold amount of movement has been detected,before the touch input has moved outside of a first region correspondingto a capture affordance (e.g., 910, 602, 1000), and/or or before thetouch input has moved into a second region associated with capture ofthe second type of media that continues after detecting liftoff (e.g.,at affordance 932)) and after the threshold amount of time (e.g., 1second) has elapsed since the touch input was detected (e.g., touch-downevent on touch screen 902), the electronic device (e.g., 600, 900)captures (1110) a second type of media (e.g., a video, including audio)that has a duration that is based on the duration of the touch input onthe touch-sensitive surface. For example, in response to exemplary tapand hold gesture touch input 930, device 900 captures a video having alength based on (e.g., equal to) the duration of the touch input. Insome embodiments, the duration of the second type of media is the sameas the duration during which the touch input was detected on thetouch-sensitive surface. For example, if the touch input duration is 8seconds, then the resulting video is 8 seconds. In some embodiments, theduration of the second type of media is the duration from when the touchinput exceeded the threshold amount of time until liftoff of the touchinput from the touch-sensitive surface. For example, if the touch inputduration is 8 seconds and the threshold amount of time is 1 second, thenthe resulting video is 7 seconds. In some embodiments, the touch inputincludes movement that does not satisfy the movement criteria forcausing a media capture session to enter a locked media capture state,and the device (e.g., 600, 900) begins capturing the second type ofmedia anyway (e.g., in response to the touch input meeting the thresholdamount of time, or in response to movement (e.g., a particular amount ofmovement in a particular direction) of the touch input). In someembodiments, the touch input has not been detected for a thresholdamount of time before the touch input meets a movement criteria (e.g.,same or different than a criteria for enabling a media capture lockstate) that causes the device (e.g., 600, 900) to begin capturing thesecond type of media anyway (e.g., in response to movement (e.g., by aminimum amount) of the touch input toward a media capture lockaffordance). FIGS. 9D-9F illustrate device 900 capturing a second typeof media, that has a duration that is based on the duration of the touchinput on the touch-sensitive surface, in accordance with a determinationthat exemplary touch input 930 is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethreshold amount of time has elapsed since the touch input was detected.

In response to detecting the touch input (1106), and in accordance witha determination that the touch input (e.g., 940, 603) meets the movementcriteria and includes movement (e.g., as shown in FIGS. 9G-9I) in afirst direction (e.g., the touch input includes more than a thresholdamount of movement (e.g., movement from a location of a media captureaffordance 910 to a location of a media capture lock affordance 932) inthe first direction (e.g., toward a first edge of the touch-sensitivesurface; from media capture affordance 910 toward media capture lockaffordance 932) or when the touch input has moved into a second regionassociated with capture of the second type of media that continues afterdetecting liftoff (e.g., at affordance 932)), the electronic device(e.g., 600, 900) starts (1112) to capture the second type of media(e.g., video) and continues to capture the second type of media afterdetecting liftoff of the touch input from the touch-sensitive surface.For example, FIGS. 9G-9J illustrate device 900 starting to capture andcontinuing to capture (after liftoff) a second type of media, inaccordance with a determination that exemplary touch input 940 meetsmovement criteria (e.g., liftoff on a location of affordance 932) andincludes movement in a first direction (e.g., toward affordance 932).For further example, FIGS. 10A-10F illustrate an exemplary touch input1002 that meets movement criteria (e.g., movement past lock distancemarker 1008 in the first direction) and includes movement in a firstdirection (e.g., to the right). In some embodiments, the device performsthe actions noted above in response to the touch input meeting themovement criteria and including movement in the first direction,regardless of whether the threshold amount of time has elapsed and/orthe timing of when the movement of the touch input begin or finishedwith respect to the threshold amount of time. For example, device 900can begin recording a video in response to a touch input (e.g., where athreshold amount of time is 1 second); after 2 minutes of detecting thatthe touch input is a stationary tap and hold (and recording video), thedevice detects that the touch input moves and meets media capturesession locking criteria—in response, the device will continue recordingafter liftoff.

In some embodiments, continuing to capture media comprises transitioninga media capture session from an unlocked media capture state to a lockedmedia capture state (e.g., also referred to as a “locked media capturesession state”). In some embodiments, the electronic device (e.g., 600,900) displays a user interface element (e.g., marker 1008, affordances932 or 1004), or other graphical indication of an amount of touch inputmovement that will satisfy a movement criteria. In some embodiments, thedevice displays more than one user interface element. In someembodiments, each user interface element can correspond to the same ordifferent movement criteria (e.g., associated with different mediacapture-related actions). For example, the device displays a graphicaluser interface element (e.g., 932, 1008) showing an area (e.g., area of932; area to the right of 1008) that indicates the amount of movementthat will cause the media capture session to enter a media capture stateand thus continue after liftoff of the touch input (e.g., 1002). In someembodiments, the movement criteria is movement less than (e.g., aportion of) the distance between the first user interface element (e.g.,1000) and the other user interface element (e.g., 1004) (e.g., asillustrated and described with respect to FIGS. 10A-10F). For example,movement and liftoff of touch input 1002 of at least 50% of the distancefrom exemplary first user interface element 1000 to the exemplary userinterface element 1004 can be sufficient to continue capture of themedia after liftoff of the touch input.

Using one or more combinations of movement criteria and a thresholdamount of time to determine whether to capture a first type of media, asecond type of media having a particular duration, and a second type ofmedia that continues being captured provides additional control optionswithout cluttering the user interface (e.g., GUI) with additionaldisplayed controls. Providing additional control options withoutcluttering the UI with additional displayed controls enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently. Further, the user can initiate a video recording using asingle technique and then, after initiating the video recording, performdifferent continuation gestures to indicate whether the device shouldquickly end the recording or extend the recording. Additionally, theuser can start a recording quickly and then decide after starting therecording whether to capture a photo, short video, or long video.Additionally, this reduced the number of controls that need to bedisplayed on the display (e.g., no need for both a still photo buttonand a video button or three different buttons for the different types ofmedia. Saving screen space is particularly important when the rest ofthe screen could be used to display a camera preview of the content thatthe user is capturing.

Using one or more combinations of movement criteria and a thresholdamount of time to determine whether to capture a first type of media, asecond type of media having a particular duration, and a second type ofmedia that continues being captured reduces the number of inputs neededto perform one or more of these operations when starting from aparticular user interface. Reducing the number of inputs needed toperform an operation enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Using movement criteria of a touch input on a user interface element,usable to cause/start capture of a (e.g., second) type of media, tocontrol whether the type of media continues being captured after liftoff the touch input captured provides additional control options withoutcluttering the user interface (e.g., GUI) with additional displayedcontrols. Providing additional control options without cluttering the UIwith additional displayed controls enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in accordance with the determination that the touchinput (e.g., 930 of FIGS. 9D-9F) is lifted from the touch-sensitivesurface (e.g., 902) before the touch input meets the movement criteriaand after the threshold amount of time has elapsed since the touch inputwas detected: the electronic device (e.g., 600, 900) ceases to capture(e.g., as shown in FIGS. 9D-9F) (e.g., ceases to record a video, andstores the resulting video in a media library) the second type of media(e.g., video) in response to detecting liftoff of the touch input (e.g.,end of recorded video duration occurs at liftoff).

In some embodiments, the first type of media has a duration that isindependent of the duration of the touch input (e.g., 920) on thetouch-sensitive surface (e.g., 902). For example the first type of mediacan be a video with fixed length (e.g., 3 seconds long) not affected bytouch input duration (e.g., on touch screen display 902), or can be astill photo or a still photo accompanied by a sequence of other photosor media such as audio content for a predefined duration before and/orafter the still photo.

In some embodiments, the movement criteria is a first movement criteria,and in response to detecting the touch input (e.g., 970) (1106), and inaccordance with a determination that the touch input meets a secondmovement criteria (e.g., movement outside of a region/location of mediacapture affordance 910 in FIGS. 9M-9N) and includes movement in a seconddirection (e.g., to the left of the location of media capture affordance910 (or stop affordance 934) in FIGS. 9M-9N) that is different from thefirst direction (e.g., to the right in FIGS. 9M-9N), the electronicdevice (e.g., 600, 900) starts (1114) to capture a sequence of mediaitems (e.g., beginning a burst image capture mode) of the first type ofmedia (e.g., still photo) where the number of media items captured isdetermined based on a duration of the touch input on the touch sensitivesurface (e.g., a duration of the touch input while it is more than thethreshold distance from the location of the user interface element(e.g., 910, 602, 1000, 934, 605) or while the touch input is in apredefined region that is associated with capturing the sequence ofmedia items of the first type of media (e.g., region to the left ofaffordances 910, 934, 602, 1000, or 605). For example, the touch inputcan meet second movement criteria if the touch input includes more thana threshold amount of movement (e.g., sufficient to enable burst mode)in a second direction that is different from (e.g., opposite to, towarda second edge of the touch-sensitive surface) the first direction (e.g.,to the right in FIGS. 9M-9N), includes or movement into a predefinedregion that is associated with capturing a sequence of media items ofthe first type of media (e.g., region to the left of media captureaffordance 910 in FIGS. 9M-9N. Capturing a sequence of media items canalso be referred to as a burst mode, burst image capture mode,continuous shooting mode, or the like.

In some embodiments, the movement satisfying the second movementcriteria occurs before the threshold amount of time. For example, themovement criteria can require that the movement in the second directionmust occur within the threshold amount of time in order for the deviceto start capturing the sequence of media items. In some embodiments, themovement begins before the threshold amount of time. For example, themovement criteria can require that the movement in the second directionmust begin before the threshold amount of time in order for the deviceto start capturing the sequence of media items (e.g., even if movementends after the threshold amount of time). In some embodiments, thesecond movement criteria can be satisfied by movement that begins afterthe threshold duration has elapsed. In some embodiments, the secondmovement criteria includes any movement (e.g., any movement in aparticular (e.g., second) direction). In some embodiments, the secondmovement criteria includes a threshold amount (e.g., a minimum distance)of movement (e.g., in the second direction). In some embodiments, thesecond movement criteria includes a requirement that the touch input hasmoved outside of a first region corresponding to a media captureaffordance (e.g., 910, 602, 1000). In some embodiments, the secondmovement criteria includes a requirement that the touch input has movedinto a second region associated with capture of the sequence of thefirst type of media item (e.g., location). In some embodiments, thefirst movement criteria and the second movement criteria are the same,but in different directions (e.g., same distance requirement, but inopposite directions).

Using one or more combinations of movement criteria and a thresholdamount of time to determine whether to capture a first type of media, asecond type of media having a particular duration, a second type ofmedia that continues being captured, and a sequence of media items ofthe first type provides additional control options without clutteringthe user interface (e.g., GUI) with additional displayed controls.Providing additional control options without cluttering the UI withadditional displayed controls enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Using one or more combinations of movement criteria and a thresholdamount of time to determine whether to capture a first type of media, asecond type of media having a particular duration, a second type ofmedia that continues being captured, and a sequence of media items ofthe first type reduces the number of inputs needed to perform one ormore of these operations when starting from a particular user interface.Reducing the number of inputs needed to perform an operation enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the touchinput (e.g., 970) meets the second movement criteria and includesmovement (e.g., sufficient to enable burst mode) in the second directionthat is different from (e.g., opposite to, toward a second edge of thetouch-sensitive surface) the first direction: the electronic device(e.g., 600, 900) ceases to capture the sequence of media items of thefirst type of media (e.g., end of duration occurs at liftoff) inresponse to detecting liftoff of the touch input (e.g., in response toliftoff of 970 at FIG. 9P). For example, in response to liftoff of touchinput 970, device 900 stops performing burst image capture (e.g.,recording still images in quick succession) (e.g., and stores thecaptured images).

In some embodiments, while continuing to capture the sequence of mediaitems of the first type of media (e.g., as shown in FIGS. 9N-9P): theelectronic device (e.g., 600, 900) displays, on the display (e.g., 902),a number of media items (e.g., 972 of FIG. 9N; 976 of FIGS. 9O-9P) ofthe first type of media that have been captured since starting tocapture the sequence of media items (e.g., wherein the number of mediaitems increases as the sequence capturing continues). In someembodiments, the number of media items is displayed at a location of thefirst user interface element on the display (e.g., location of the mediacapture affordance 910 as shown in FIG. 9M). In some embodiments, thenumber of media items displayed is based on the number of media itemsthat have been captured since touch input was detected.

In some embodiments, displaying, on the display (e.g., 902), the numberof media items of the first type of media that have been captured sincestarting to capture the sequence of media items includes: the electronicdevice (e.g., 600, 900) displaying, on the display, the number of mediaitems of the first type of media that have been captured at an initiallocation (e.g., location of 972 of FIG. 9N) on the display. Inaccordance with a determination that the touch input (e.g., 970)includes movement to a location on the touch-sensitive surface thatcorresponds to the initial location on the display (e.g., touch input970 moves as shown in FIGS. 9N-9O): the electronic device displays, onthe display, the number of media items (e.g., 976 of FIGS. 9O-9P), ofthe first type of media, at the location of the first user interfaceelement (e.g., in FIG. 9O, 976 is now displayed at the same location asmedia capture affordance 910 as shown in FIG. 9M) on the display. Theelectronic device ceases to display the number of media items, of thefirst type of media, at the initial location on the display (e.g., 972is no longer displayed in FIGS. 9O-9P).

Displaying a number of media items that have been captured at a newlocation in accordance with movement of a touch input to an initiallocation provides improved visual feedback that prevents the informationfrom be obscured by the touch input. Providing improved feedbackenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the electronic device (e.g., 600, 900) displays(1116), on the display (e.g., 902), a second user interface element(e.g., a icon, affordance, or distance marker) (e.g., media capture lockaffordance 932; media capture lock affordance 1004, lock distance marker1008) wherein movement of the touch input (e.g., 940, 603) from thefirst user interface element (e.g., location of 910, location of 934,location of 1000, location of 602, location of 605) to the second userinterface element (e.g., 932, 1004, 1008) meets the movement criteria(e.g., the movement criteria includes detecting a threshold amount ofmovement (e.g., in a direction) toward the second user interfaceelement, or movement to the first region (e.g., region of the seconduser interface element) associated with capturing the second type ofmedia that continues to be captured after liftoff). In some embodiments,liftoff of the touch input at a location corresponding to the seconduser interface element (e.g., at a location of 932 or 1004; in a regionto the fight of marker 1008) is required for the second type of media tocontinue being recorded after liftoff.

Displaying a user interface element that satisfies movement criteriaprovides improved visual feedback regarding the input movement needed toperform an action. Providing improved feedback enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.)

In some embodiments, in accordance with continuing to capture the secondtype of media after detecting liftoff of the touch input (e.g., 940,603) from the touch-sensitive surface (e.g., 902), the electronic device(e.g., 600, 900) changes the second user interface element (e.g., 932 inFIG. 9I) to a third user interface element (e.g., 944 in FIG. 9J)different from the second user element. In some embodiments, the seconduser interface element changes in response to movement of the touchinput. In some embodiments, the second user interface element changes inresponse to liftoff of the touch input (e.g., at a location of a mediacapture lock affordance). In some embodiments, the second user interfaceelement changes in response to the media captures session entering alocked media capture state.

In some embodiments, the second user interface element (e.g., 932)changes to the third user interface element (e.g., 944) in response toan interaction between the touch input (e.g., 940, 603) and a locationon the touch-sensitive surface corresponding to the second userinterface element (e.g., the location of the user interface element932). For example, an interaction can occur when touch input 940 isdragged to the location of the media capture lock affordance 932. Forfurther example, an interaction can occur when touch input 940 lifts offwhen at the location of media capture lock affordance 932).

In some embodiments, the touch input (e.g., 940, 603) is a first touchinput, and while continuing to capture the second type of media (e.g.,video): the electronic device (e.g., 600, 900) detects, via thetouch-sensitive surface (e.g., 902), a second touch input (e.g., 960) ata location on the touch-sensitive surface that corresponds to the thirduser interface element (e.g., 944). In response to detecting the secondtouch input, the electronic device captures the first type of media(e.g., takes a still photo) (e.g., while continuing to capture thesecond type of media).

In some embodiments, while detecting the touch input (e.g., 940, 603) onthe touch-sensitive surface (e.g., right after touch-down, or rightafter movement of the touch input in the first direction), theelectronic device (e.g., 600, 900) displays (1118), on the display(e.g., 902), a directional indicator (e.g., 943, 975, 1005, 604 a, 604b) in the first direction from a location of the first user interfaceelement (e.g., location of 910, location of 934, location of 1000,location of 602, location of 605) on the display.

In some embodiments, the directional indicator (e.g., 943, 975, 1005,604 a, 604 b) can include one or more of: a line (e.g., solid, dotted,dashed), an arrow, an animation, and other graphical indication of adirection (e.g., that satisfies a movement criteria). In someembodiments, the directional indicator indicates an amount of movementneeded to meet the movement criteria (e.g., movement path indicator 1005that includes lock distance marker 1008). In some embodiments, thedirectional indicator indicates a region or location to which the touchinput needs to be moved to meet the movement criteria (e.g., movementpath indicator 1005 that lock distance marker 1008) (e.g., with orwithout requiring touch input liftoff).

Displaying a directional indicator provides improved visual feedbackregarding the input movement needed to perform an action. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the directional indicator (e.g., 943, 975, 1005,604 a, 604 b) is displayed in accordance with a determination that thetouch input (e.g., 940, 603) includes movement in the first direction.For example, movement path indicator 943 is not displayed until touchinput 940 begins moving (e.g., toward media capture lock affordance932). In some embodiments, the device displays the movement pathindicator in response to detecting the touch input, or in response todetecting the touch input for a threshold amount of time.

In some embodiments, in accordance with continuing to capture the secondtype of media (e.g., video) after detecting liftoff of the touch input(e.g., liftoff of 940 in FIGS. 9I-9J, liftoff of 603) from thetouch-sensitive surface (e.g., 902), the electronic device (e.g., 600,900) changes (1120) the first user interface element (e.g., 910, 602,1000) to a fourth user interface element (e.g., 934 in FIG. 9J, 605 inFIGS. 6D-6F). In some embodiments, the first user interface elementchanges to the fourth user interface element in accordance withbeginning to capture the second type of media (e.g., as shown in FIG.9H). In some embodiments, the first user interface element changes tothe fourth user interface element in accordance with movement of thetouch input (e.g., out of the area corresponding to the first userinterface element (e.g., as shown in FIGS. 10A-10D). In someembodiments, the electronic device changes the first user interfaceelement to the fourth user interface element in response to liftoff ofthe touch input.

Changing a user interface element in accordance with continuing tocapture second type of media provides relevant alternative controloptions without cluttering the user interface (e.g., GUI) withadditional displayed controls. Providing additional control optionswithout cluttering the UI with additional displayed controls enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the touch input (e.g., 940, 603) is a first touchinput, and while continuing to capture the second type of media afterdetecting liftoff of the touch input (e.g., 940, 603) from thetouch-sensitive surface (e.g., 902), the electronic device (e.g., 600,900) detects, via the touch-sensitive surface, a third touch input(e.g., 950, 606) at a location on the touch-sensitive surface thatcorresponds to the fourth user interface element (e.g., 934, 605). Inresponse to detecting the third touch input, the electronic deviceceases to capture the second type of media (e.g., stops recording video,and stores the recorded video in a media library).

In some embodiments, the first type of media is one or more of: a stillimage and a video (e.g., video clip having a fixed duration, and/or aduration independent of a duration of the touch input).

In some embodiments, capturing the first type of media, by the one ormore media capture components (e.g., camera, image sensor), occurs: inresponse to detecting the touch input (e.g., 603, 920, 930, 940, 970,1002) on the touch-sensitive surface (e.g., touch-down on 902) or inresponse to liftoff of the touch input from the touch-sensitive surface.In some embodiments, capturing the first type of media occurs while thetouch input is detected on the touch-sensitive surface.

In some embodiments, the second type of media is a video (e.g., havingduration related to length of touch input, or until a stop affordance(e.g., 934, 605) is selected).

In some embodiments, capturing the second type of media, by the one ormore media capture components (e.g., camera, image sensor), comprisesbeginning to record the video in response to the touch input beingdetected on the touch-sensitive surface for more than the thresholdamount of time (e.g., 1 second).

In some embodiments, in accordance with a determination that the touchinput (e.g., 930) is lifted from the touch-sensitive surface before thetouch input meets the movement criteria (e.g., media capture session isnot in a locked media capture state) and after the threshold amount oftime (e.g., 1 second) (e.g., device has begun recording video) haselapsed since the touch input was detected: the electronic device (e.g.,600, 900) captures the first type of media (e.g., still image), anddiscards (e.g., deleting before or after adding the first type of mediato a media library) the captured first type of media. For example, theelectronic device can capture a first type of media item in accordancewith receiving a touch input (e.g., in response to touch-down of touchinput 930). After the touch input meets criteria for capturing a secondtype of media, the device can discard the captured first type of media(e.g., because the characteristics of the touch input gesturesubsequently indicate that the capture of the first media item is notintended).

Capturing first media so that if the user lifts off it is available, butautomatically deleting it conserves storage space when the user startsrecording other content (e.g., second media, such as a video), whichindicates that the first media (e.g., a photo) is not needed. Furtherautomatically discarding the first media based on other media beingcaptured (e.g., beginning to record a video) reduces the number of userinputs needed to discard the media. Reducing the number of inputs neededto perform an operation enhances the operability of the device and makesthe user-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 1100 (e.g., FIG. 11) are also applicable in an analogous mannerto the methods described below/above. For example, method 1100optionally includes one or more of the characteristics of the variousmethods described above with reference to method 700. For brevity, thesedetails are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to performgesture-based media capture. The present disclosure contemplates that insome instances, this gathered data may include personal information datathat uniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, twitter IDs,home addresses, data or records relating to a user's health or level offitness (e.g., vital signs measurements, medication information,exercise information), date of birth, or any other identifying orpersonal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. Further, other uses for personal information data that benefitthe user are also contemplated by the present disclosure. For instance,health and fitness data may be used to provide insights into a user'sgeneral wellness, or may be used as positive feedback to individualsusing technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof a media capture application, the present technology can be configuredto allow users to select to “opt in” or “opt out” of participation inthe collection of personal information data during registration forservices or anytime thereafter. In addition to providing “opt in” and“opt out” options, the present disclosure contemplates providingnotifications relating to the access or use of personal information. Forinstance, a user may be notified upon downloading an app that theirpersonal information data will be accessed and then reminded again justbefore personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, media contentcan be captured and stored by inferring user intention based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to amedia capture interface application, or publicly available information.

What is claimed is:
 1. An electronic device, comprising: a display; atouch-sensitive surface; one or more media capture components; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors, the one or more programsincluding instructions for: displaying, on the display, a first userinterface element; detecting, via the touch-sensitive surface, a touchinput that begins at a location on the touch-sensitive surface thatcorresponds to the first user interface element; and in response todetecting the touch input: in accordance with a determination that thetouch input is lifted from the touch-sensitive surface before the touchinput meets movement criteria and before a threshold amount of time haselapsed since the touch input was detected, capturing a first type ofmedia; in accordance with a determination that the touch input is liftedfrom the touch-sensitive surface before the touch input meets themovement criteria and after the threshold amount of time has elapsedsince the touch input was detected, capturing a second type of mediathat has a duration that is based on the duration of the touch input onthe touch-sensitive surface; in accordance with a determination that thetouch input meets the movement criteria and includes movement in a firstdirection, wherein movement of the touch input from the first userinterface element to a displayed second user interface element meets themovement criteria: starting to capture the second type of media andcontinuing to capture the second type of media after detecting liftoffof the touch input from the touch-sensitive surface; and in accordancewith continuing to capture the second type of media after detectingliftoff of the touch input from the touch-sensitive surface, changingthe second user interface element to a third user interface elementdifferent from the second user interface element.
 2. The electronicdevice of claim 1, the one or more programs further includinginstructions for: in accordance with the determination that the touchinput is lifted from the touch-sensitive surface before the touch inputmeets the movement criteria and after the threshold amount of time haselapsed since the touch input was detected: ceasing to capture thesecond type of media in response to detecting liftoff of the touchinput.
 3. The electronic device of claim 1, wherein the first type ofmedia has a duration that is independent of the duration of the contacton the touch-sensitive surface.
 4. The electronic device of claim 1,wherein the movement criteria is a first movement criteria, the one ormore programs further including instructions for, in response todetecting the touch input: in accordance with a determination that thetouch input meets a second movement criteria and includes movement in asecond direction that is different from the first direction, starting tocapture a sequence of media items of the first type of media where thenumber of media items captured is determined based on a duration of thetouch input on the touch sensitive surface.
 5. The electronic device ofclaim 4, the one or more programs further including instructions for: inaccordance with a determination that the touch input meets the secondmovement criteria and includes movement in the second direction that isdifferent from the first direction: ceasing to capture the sequence ofmedia items of the first type of media in response to detecting liftoffof the touch input.
 6. The electronic device of claim 4, the one or moreprograms further including instructions for, while continuing to capturethe sequence of media items of the first type of media: displaying, onthe display, a number of media items of the first type of media thathave been captured since starting to capture the sequence of mediaitems, wherein the number of media items are displayed at a location ofthe first user interface element on the display.
 7. The electronicdevice of claim 6, wherein displaying, on the display, the number ofmedia items of the first type of media that have been captured sincestarting to capture the sequence of media items includes: displaying, onthe display, the number of media items of the first type of media thathave been captured at an initial location on the display; and inaccordance with a determination that the touch input includes movementto a location on the touch-sensitive surface that corresponds to theinitial location on the display: displaying, on the display, the numberof media items, of the first type of media, at the location of the firstuser interface element on the display; and ceasing to display the numberof media items, of the first type of media, at the initial location onthe display.
 8. The electronic device of claim 1, the one or moreprograms further including instructions for: displaying, on the display,a second user interface element, wherein movement of the touch inputfrom the first user interface element to the second user interfaceelement meets the movement criteria.
 9. The electronic device of claim8, the one or more programs further including instructions for: inaccordance with continuing to capture the second type of media afterdetecting liftoff of the touch input from the touch-sensitive surface,changing the second user interface element to a third user interfaceelement different from the second user element.
 10. The electronicdevice of claim 9, wherein the second user interface element changes tothe third user interface element in response to an interaction betweenthe touch input and a location on the touch-sensitive surfacecorresponding to the second user interface element.
 11. The electronicdevice of claim 9, wherein the touch input is a first touch input, theone or more programs further including instructions for: whilecontinuing to capture the second type of media: detecting, via thetouch-sensitive surface, a second touch input at a location on thetouch-sensitive surface that corresponds to the third user interfaceelement; and in response to detecting the second touch input, capturingthe first type of media.
 12. The electronic device of claim 1, the oneor more programs further including instructions for: while detecting thetouch input on the touch-sensitive surface, displaying, on the display,a directional indicator in the first direction from a location of thefirst user interface element on the display.
 13. The electronic deviceof claim 12, wherein the directional indicator is displayed inaccordance with a determination that the touch input includes movementin the first direction.
 14. The electronic device of claim 1, the one ormore programs further including instructions for: in accordance withcontinuing to capture the second type of media after detecting liftoffof the touch input from the touch-sensitive surface, changing the firstuser interface element to a fourth user interface element.
 15. Theelectronic device of claim 14, wherein the touch input is a first touchinput, the one or more programs further including instructions for:while continuing to capture the second type of media after detectingliftoff of the touch input from the touch-sensitive surface, detecting,via the touch-sensitive surface, a third touch input at a location onthe touch-sensitive surface that corresponds to the fourth userinterface element; and in response to detecting the third touch input,ceasing to capture the second type of media.
 16. The electronic deviceof claim 1, wherein the first type of media is one or more of: a stillimage and a video.
 17. The electronic device of claim 16, whereincapturing the first type of media, by the one or more media capturecomponents, occurs: in response to detecting the touch input on thetouch-sensitive surface or in response to liftoff of the touch inputfrom the touch-sensitive surface.
 18. The electronic device of claim 1,wherein the second type of media is a video.
 19. The electronic deviceof claim 18, wherein capturing, by the one or more media capturecomponents, the second type of media comprises beginning to record thevideo in response to the touch input being detected on thetouch-sensitive surface for more than the threshold amount of time. 20.The electronic device of claim 1, the one or more programs furtherincluding instructions for: in accordance with a determination that thetouch input is lifted from the touch-sensitive surface before the touchinput meets the movement criteria and after the threshold amount of timehas elapsed since the touch input was detected: capturing the first typeof media; and discarding the captured first type of media.
 21. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display, a touch-sensitive surface, and one ormore media capture components, the one or more programs includinginstructions for: displaying, on the display, a first user interfaceelement; detecting, via the touch-sensitive surface, a touch input thatbegins at a location on the touch-sensitive surface that corresponds tothe first user interface element; and in response to detecting the touchinput: in accordance with a determination that the touch input is liftedfrom the touch-sensitive surface before the touch input meets movementcriteria and before a threshold amount of time has elapsed since thetouch input was detected, capturing a first type of media; in accordancewith a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets the movementcriteria and after the threshold amount of time has elapsed since thetouch input was detected, capturing a second type of media that has aduration that is based on the duration of the touch input on thetouch-sensitive surface; in accordance with a determination that thetouch input meets the movement criteria and includes movement in a firstdirection, wherein movement of the touch input from the first userinterface element to a displayed second user interface element meets themovement criteria: starting to capture the second type of media andcontinuing to capture the second type of media after detecting liftoffof the touch input from the touch-sensitive surface; and in accordancewith continuing to capture the second type of media after detectingliftoff of the touch input from the touch-sensitive surface, changingthe second user interface element to a third user interface elementdifferent from the second user interface element.
 22. Acomputer-implemented method, comprising: at an electronic device with adisplay, a touch-sensitive surface, and one or more media capturecomponents: displaying, on the display, a first user interface element;detecting, via the touch-sensitive surface, a touch input that begins ata location on the touch-sensitive surface that corresponds to the firstuser interface element; and in response to detecting the touch input: inaccordance with a determination that the touch input is lifted from thetouch-sensitive surface before the touch input meets movement criteriaand before a threshold amount of time has elapsed since the touch inputwas detected, capturing a first type of media; in accordance with adetermination that the touch input is lifted from the touch-sensitivesurface before the touch input meets the movement criteria and after thethreshold amount of time has elapsed since the touch input was detected,capturing a second type of media that has a duration that is based onthe duration of the touch input on the touch-sensitive surface; inaccordance with a determination that the touch input meets the movementcriteria and includes movement in a first direction, wherein movement ofthe touch input from the first user interface element to a displayedsecond user interface element meets the movement criteria: starting tocapture the second type of media and continuing to capture the secondtype of media after detecting liftoff of the touch input from thetouch-sensitive surface; and in accordance with continuing to capturethe second type of media after detecting liftoff of the touch input fromthe touch-sensitive surface, changing the second user interface elementto a third user interface element different from the second userinterface element.